System and Method to Enable Resource Partitioning in Wireless Networks

ABSTRACT

Systems and methodologies are described that facilitate improved resource partitioning and interference management in a wireless communication system. Techniques are described herein for the transmission and use of various types of signaling, such as Access Request commands, Reverse Link Special Resource Utilization Message (R-SRUM) signaling, Forward Link Special Resource Utilization Message (F-SRUM) signaling, and the like, for managing interference associated with range extension, restricted association networks, and other jamming scenarios. As described herein, downlink resource coordination and interference management are accomplished through the use of Access Request or R-SRUM signaling conducted in a unicast or broadcast fashion, and uplink resource coordination and interference management are accomplished through the use of F-SRUM signaling. As further described herein, a clean communication channel such as a Low Reuse Preamble (LRP) channel can be utilized for interference management signaling and/or leveraged for determining timing of various signaling messages.

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

This is a continuation application of U.S. application Ser. No.12/465,422 filed on May 13, 2009, which claims the benefit of U.S.Provisional Application Ser. No. 61/055,384, filed May 22, 2008, andentitled “SYSTEM AND METHOD TO ENABLE RESOURCE PARTITIONING IN WIRELESSNETWORKS,” each of which is incorporated herein by reference in itsentirety. This application is related to U.S. application Ser. No.12/465,413, filed May 13, 2009, which is also incorporated herein byreference in its entirety.

BACKGROUND

I. Field

The present disclosure relates generally to wireless communications, andmore specifically to techniques for resource and interference managementin a wireless communication system.

II. Background

Wireless communication systems are widely deployed to provide variouscommunication services; for instance, voice, video, packet data,broadcast, and messaging services can be provided via such wirelesscommunication systems. These systems can be multiple-access systems thatare capable of supporting communication for multiple terminals bysharing available system resources. Examples of such multiple-accesssystems include Code Division Multiple Access (CDMA) systems, TimeDivision Multiple Access (TDMA) systems, Frequency Division MultipleAccess (FDMA) systems, and Orthogonal Frequency Division Multiple Access(OFDMA) systems.

As the demand for high-rate and multimedia data services rapidly grows,there has been an effort toward implementation of efficient and robustcommunication systems with enhanced performance. For example, in recentyears, users have started to replace fixed line communications withmobile communications and have increasingly demanded great voicequality, reliable service, and low prices.

In addition to mobile telephone networks currently in place, a new classof small base stations has emerged, which can be installed in the homeof a user and provide indoor wireless coverage to mobile units usingexisting broadband Internet connections. Such personal miniature basestations are generally known as access point base stations, or,alternatively, Home Node B (HNB) or Femto cells. Typically, suchminiature base stations are connected to the Internet and the network ofa mobile operator via a Digital Subscriber Line (DSL) router, cablemodem, or the like.

Wireless communication systems can be configured to include a series ofwireless access points, which can provide coverage for respectivelocations within the system. Such a network structure is generallyreferred to as a cellular network structure, and access points and/orthe locations they respectively serve in the network are generallyreferred to as cells.

In conventional wireless network implementations, a set of base stationsare utilized to provide network coverage for respective geographic areascorresponding to the base stations. Further, power levels of respectivebase stations in a wireless network can differ from base station to basestation, based on factors such as the relative sizes of areas covered bythe base stations and/or other such factors. For example, macro basestations can be configured to cover a large area and utilize a largepower class, while pico base stations and/or femto base stations can beconfigured to cover a smaller area and utilize lower power.

Accordingly, in a scenario in which a mobile terminal is located betweentwo base stations of varying power levels, the mobile terminal canselect a base station from the neighboring base stations to which toconnect based on a variety of factors. However, in the case that themobile terminal establishes communication with a base station having arelatively low power level, the terminal may become jammed by one ormore neighboring base stations with higher power. A similar scenario canoccur on the uplink, wherein a mobile terminal communicating at arelatively high level of power to a base station that is far away cancause jamming to the uplink communication of one or more base stationsthat are closer to the mobile terminal.

Further, in dominant interference conditions such as those describedabove, a regular access request transmitted by a mobile terminal to adesired serving base station can in some cases fail to be received bythe base station due to uplink interference. Additionally, if the basestation recognizes the regular access request and responds to it, theterminal may in some cases be unable to receive the response due todownlink interference. Accordingly, it would be desirable to implementimproved initial access and/or interference management techniques forwireless networks that mitigate at least the above shortcomings withrespect to dominant interference conditions.

SUMMARY

The following presents a simplified summary of various aspects of theclaimed subject matter in order to provide a basic understanding of suchaspects. This summary is not an extensive overview of all contemplatedaspects, and is intended to neither identify key or critical elementsnor delineate the scope of such aspects. Its sole purpose is to presentsome concepts of the disclosed aspects in a simplified form as a preludeto the more detailed description that is presented later.

According to an aspect, a method operable in a wireless communicationsystem is described herein. The method can comprise identifying acommunication channel utilized by a wireless communication system;detecting one or more interfering base stations; and transmittinginterference reduction requests to respective detected interfering basestations over the communication channel.

A second aspect described herein relates to a wireless communicationsapparatus that can comprise a memory that stores data relating to acommunication channel and at least one base station causing jamming tothe wireless communications apparatus. The wireless communicationsapparatus can further comprise a processor configured to transmitrespective resource clearing requests to the at least one base stationover the communication channel.

A third aspect relates to an apparatus operable in a wirelesscommunication system. The apparatus can comprise means for identifyingone or more interfering Node Bs; means for identifying a communicationchannel designated for resource partitioning signaling; and means fortransmitting resource utilization signaling to respectively identifiedinterfering Node Bs, wherein the resource utilization signalingspecifies a set of set of resources requested to be reserved by therespective interfering Node Bs.

A fourth aspect described herein relates to a computer program product,which can comprise a computer-readable medium that comprises code forcausing a computer to identify a communication channel; code for causinga computer to identify one or more Evolved Node Bs (eNBs) causinginterference on selected predetermined set of resources; and code forcausing a computer to transmit respective resource utilization messagesto identified interfering eNBs over the communication channel, whereinthe reverse link resource utilization messages request clearing of thepredetermined set of resources.

A fifth aspect described herein relates to a method used in a wirelesscommunication system. The method can comprise receiving an interferencereduction request from a terminal; identifying a set of downlinkcommunication resources provided in the interference reduction request;calculating an amount of interference caused to the terminal; andreserving the set of downlink communication resources provided in theinterference reduction request upon determining that the amount ofinterference caused to the terminal exceeds a predefined threshold.

A sixth aspect described herein relates to a wireless communicationsapparatus that can comprise a memory that stores data relating to a userequipment unit (UE) and a broadcast message received from the UE. Thewireless communications apparatus can further include a processorconfigured to identify a set of downlink communication resourcesspecified in the broadcast message, to calculate an amount ofinterference the wireless communications apparatus is imposing on theUE, and to set aside the set of downlink communication resources upondetermining that the calculated amount of interference is greater thanor equal to a threshold value.

A seventh aspect relates to an apparatus that can be utilized in awireless communication system. The apparatus can comprise means forreceiving access signaling from a terminal; means for identifying aresource set specified in the access signaling; means for calculatinginterference caused to the terminal by the apparatus; and means forsetting aside resources in the resource set specified in the accesssignaling if the calculated interference meets or exceeds a threshold.

An eighth aspect described herein relates to a computer program product,which can include a computer-readable medium that comprises code forcausing a computer to identify a UE and an access request messagereceived from the UE; code for causing a computer to extract informationrelating to a desired set of communication resources from the accessrequest message; code for causing a computer to determine an amount ofinterference imposed on the UE; and code for causing a computer to setaside the desired set of resources specified in the access requestmessage upon determining that the determined amount of interference isgreater than or equal to a predefined permissible amount ofinterference.

To the accomplishment of the foregoing and related ends, one or moreaspects of the claimed subject matter comprise the features hereinafterfully described and particularly pointed out in the claims. Thefollowing description and the annexed drawings set forth in detailcertain illustrative aspects of the claimed subject matter. Theseaspects are indicative, however, of but a few of the various ways inwhich the principles of the claimed subject matter can be employed.Further, the disclosed aspects are intended to include all such aspectsand their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system for coordinating control resourceswithin a wireless communication system in accordance with variousaspects.

FIGS. 2-4 illustrate respective jamming scenarios in which variousresource coordination techniques described herein can be implemented.

FIG. 5 is a block diagram of a system for utilizing unicast messages fordownlink resource coordination in accordance with various aspects.

FIG. 6 illustrates a technique for performing incremental downlinkresource coordination in accordance with various aspects.

FIG. 7 illustrates a technique for timing resource coordinationmessaging in accordance with various aspects.

FIG. 8 is a block diagram of a system for utilizing broadcast messagesfor downlink resource coordination in accordance with various aspects.

FIG. 9 is a block diagram of a system for conducting uplink resourcecoordination in accordance with various aspects.

FIG. 10 illustrates a technique for timing resource coordinationmessaging in accordance with various aspects.

FIG. 11 illustrates a technique for connecting to a network cell via anintervening cell in accordance with various aspects.

FIGS. 12-14 are flow diagrams of respective methodologies for unicastmessaging for downlink resource partitioning in a wireless communicationsystem.

FIGS. 15-16 are flow diagrams of respective methodologies for broadcastmessaging for downlink resource partitioning in a wireless communicationsystem.

FIGS. 17-18 are flow diagrams of respective methodologies for uplinkresource partitioning in a wireless communication system.

FIGS. 19-23 are block diagrams of respective apparatus that facilitateresource coordination among entities in a wireless communication system.

FIG. 24 is a timing diagram that illustrates an example access procedurethat can be utilized in accordance with various aspects.

FIG. 25 illustrates an example wireless communication system inaccordance with various aspects set forth herein.

FIG. 26 is a block diagram illustrating an example wirelesscommunication system in which various aspects described herein canfunction.

FIG. 27 illustrates an example communication system that enablesdeployment of access point base stations within a network environment.

DETAILED DESCRIPTION

Various aspects of the claimed subject matter are now described withreference to the drawings, wherein like reference numerals are used torefer to like elements throughout. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of one or more aspects. It maybe evident, however, that such aspect(s) may be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form in order to facilitate describing one ormore aspects.

As used in this application, the terms “component,” “module,” “system,”and the like are intended to refer to a computer-related entity, eitherhardware, firmware, a combination of hardware and software, software, orsoftware in execution. For example, a component can be, but is notlimited to being, a process running on a processor, an integratedcircuit, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a computing device and the computing device can be a component. Oneor more components can reside within a process and/or thread ofexecution and a component can be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components can communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems by way of the signal).

Furthermore, various aspects are described herein in connection with awireless terminal and/or a base station. A wireless terminal can referto a device providing voice and/or data connectivity to a user. Awireless terminal can be connected to a computing device such as alaptop computer or desktop computer, or it can be a self containeddevice such as a personal digital assistant (PDA). A wireless terminalcan also be called a system, a subscriber unit, a subscriber station,mobile station, mobile, remote station, access point, remote terminal,access terminal, user terminal, user agent, user device, or userequipment (UE). A wireless terminal can be a subscriber station,wireless device, cellular telephone, PCS telephone, cordless telephone,a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL)station, a personal digital assistant (PDA), a handheld device havingwireless connection capability, or other processing device connected toa wireless modem. A base station (e.g., access point or Node B) canrefer to a device in an access network that communicates over theair-interface, through one or more sectors, with wireless terminals. Thebase station can act as a router between the wireless terminal and therest of the access network, which can include an Internet Protocol (IP)network, by converting received air-interface frames to IP packets. Thebase station also coordinates management of attributes for the airinterface.

Moreover, various functions described herein can be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions can be stored on or transmitted over as oneor more instructions or code on a computer-readable medium.Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media can be anyavailable media that can be accessed by a computer. By way of example,and not limitation, such computer-readable media can comprise RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tocarry or store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc (BD), where disks usuallyreproduce data magnetically and discs reproduce data optically withlasers. Combinations of the above should also be included within thescope of computer-readable media.

Various techniques described herein can be used for various wirelesscommunication systems, such as Code Division Multiple Access (CDMA)systems, Time Division Multiple Access (TDMA) systems, FrequencyDivision Multiple Access (FDMA) systems, Orthogonal Frequency DivisionMultiple Access (OFDMA) systems, Single Carrier FDMA (SC-FDMA) systems,and other such systems. The terms “system” and “network” are often usedherein interchangeably. A CDMA system can implement a radio technologysuch as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRAincludes Wideband-CDMA (W-CDMA) and other variants of CDMA.Additionally, CDMA2000 covers the IS-2000, IS-95 and IS-856 standards. ATDMA system can implement a radio technology such as Global System forMobile Communications (GSM). An OFDMA system can implement a radiotechnology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB),IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc.UTRA and E-UTRA are part of Universal Mobile Telecommunication System(UMTS). 3GPP Long Term Evolution (LTE) is an upcoming release that usesE-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink.UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from anorganization named “3rd Generation Partnership Project” (3GPP). Further,CDMA2000 and UMB are described in documents from an organization named“3rd Generation Partnership Project 2” (3GPP2).

Various aspects will be presented in terms of systems that can include anumber of devices, components, modules, and the like. It is to beunderstood and appreciated that the various systems can includeadditional devices, components, modules, etc. and/or can not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches can also be used.

Referring now to the drawings, FIG. 1 illustrates a system 100 forcoordinating control resources within a wireless communication system inaccordance with various aspects. As FIG. 1 illustrates, system 100 caninclude one or more base stations 110, which can communicate with one ormore terminals 120 b. While only one base station 110 and terminal 120are illustrated in FIG. 1, it should be appreciated that system 100 caninclude any number of base stations 110 and/or terminals 120. Further,it can be appreciated that respective base stations 110 in system 100can serve any suitable coverage area, such as an area associated with amacro cell, a femto cell (e.g., an access point base station or HomeNode B (HNB)), and/or any other suitable type of coverage area.

In accordance with one aspect, terminal 120 can communicate with a basestation 110 designated as a serving eNB for terminal 120. For example,terminal 120 can conduct one or more uplink (UL, also referred to asreverse link (RL)) communications to base station 110, and base station110 can conduct one or more downlink (DL, also referred to as forwardlink (FL)) communications to terminal 120. In one example, uplink and/ordownlink communication between terminal 120 and base station 110 canadditionally result in interference to nearby base stations and/orterminals (not shown). For example, in a system with multiple basestations 110 and/or terminals 120, a terminal located in an area thatlies in an overlap between the coverage of respective base stations cancause interference to one or more base stations within range of theterminal with which the terminal is not communicating and/or otherterminals under various circumstances.

Specific examples in which the above-described interference can occurare illustrated as shown in FIGS. 2-4. Referring first to FIG. 2, adiagram of a system 200 is provided to illustrate an exampleinterference scenario associated with range extension. As illustrated bysystem 200, a user equipment unit (UE) 220 can be located with respectto a set of multiple Evolved Node Bs (eNBs) 212-214 such that thecoverage areas of eNBs 212-214 overlap at the location of UE 220. Asfurther illustrated, a first eNB 212 can communicate using a relativelyhigh rate of power (e.g., P_(high)), while a second eNB 214 cancommunicate using a lower power rate (e.g., P_(low)). The differences inpower levels between eNBs 212 and 214 can be due to, for example,differences in configurations of the respective eNBs 212-214, differenteNB classes (e.g., in the scenario where eNB 212 is a macro cell and eNB214 is a pico or femto cell), or the like.

In one example, it can be appreciated that UE 220 can establish aconnection with an eNB 212 or 214 within range of UE 220 that exhibitsthe least path loss. For example, on the uplink, UE 220 can connect toan eNB 214 with the lowest path loss as, for a fixed transmit power fromUE 220, an eNB 214 with the lowest path loss will similarly exhibit themaximum receive power. Further, on the downlink, even if the receivedpower from a high-power eNB 212 to UE 220 is greater than the receivedpower from an eNB 214 with lower power, UE 220 can nonetheless elect toconnect to the low-power eNB 214 in order to reduce overall systeminterference and/or to produce cell splitting gains, increasedthroughput, or other positive effects on the performance of system 200.As such a connection extends the range of weaker eNBs such as eNB 214,it is generally referred to in the art as a “range extension” or “rangeexpansion” mode.

In accordance with one aspect as illustrated by system 200, to enablerange extension, UE 220 can be required to connect to an eNB 214 whosereceive power is lower than that of other eNBs 212 in system 200.Following a connection between eNB 214 and UE 220, eNB 214 can conductone or more transmissions to UE 220, which are illustrated in FIG. 2 asa solid line. However, as UE 220 is located in the overlap of coveragearea between eNBs 212 and 214, UE 220 can additionally experienceinterfering transmissions from eNB 212, which are illustrated in FIG. 2as a dashed line. In one example, in the event that eNB 212 is morepowerful than eNB 214, interfering transmissions from eNB 212 can jam UE220, rendering it substantially unable to detect or decode desiredtransmissions from eNB 214.

A second example interference scenario that relates to network cellswith restricted association is illustrated by system 300 in FIG. 3. Asillustrated by FIG. 3, system 300 can include a femto cell 310 having anassociated coverage area 312 and a macro cell 320 that provides coveragefor an area including the coverage area 312 of femto cell 310. Further,system 300 can include a UE 330 that is located within the coverage area312 of femto cell 310.

In one example, femto cell 310 can restrict association therewith suchthat, for example, UE 330 is not permitted to connect to femto cell 310.In such a case, UE 330 can be required to connect to macro cell 320 thatserves the location of UE 330 rather than femto cell 310. However, sucha scenario can result in both uplink jamming of femto cell 310 anddownlink jamming of UE 330. More particularly, communications betweenmacro cell 320 and UE 330, which are illustrated in FIG. 3 by a solidline, can cause jamming and/or interference to the uplink of femto cell310, and communications between femto cell 310 and UEs served by femtocell 310 can cause interference and/or jamming to the downlink of UE 330due to the fact that the observed signal strength of femto cell 310 atthe location of UE 330 can be significantly larger than that of macrocell 320. Such interference between femto cell 310 and UE 330 isillustrated in FIG. 3 as a dashed line.

A third example interference scenario is illustrated by system 400 inFIG. 4, which relates to uplink interference that can be experienced ata femto cell and/or one or more other cells 414 in an associatednetwork. In the example illustrated by system 400, a set of multiplenetwork cells 412-414 can provide coverage for a geographic area thatincludes the location of a given UE 422. In one example, UE 422 canestablish a connection with a first network cell 412 such that UE 422can conduct one or more transmissions to cell 412, which are illustratedin FIG. 4 as a solid line. However, as UE 422 is also within the areaserved by cell 414 in system 400, it can be appreciated thatcommunications from UE 422 to cell 412 can additionally causeinterference at cell 414, which is illustrated in FIG. 4 as a dashedline. Such interference can, in turn, jam cell 414 on the reverse linksuch that other UEs 424 served by cell 414 are unable to connect to cell414. The extent to which cell 414 is jammed by interfering transmissionsfrom UE 422 can be based on, for example, the relative power level of UE422, relative distances of UE 422 and other UEs 424 from cell 414,and/or other factors.

Returning to FIG. 1, in view of the interference scenarios illustratedby FIGS. 2-4 and/or any other applicable causes of interference,respective entities in system 100 can in accordance with one aspectengage in resource coordination to mitigate interference experiencedwithin system 100. To these ends, base station 110 can include aresource coordination module 112, which can operate to coordinatecontrol resource usage between base station 110 and terminal 120 tomitigate the effects of interference between entities in system 100.Similarly, terminal 120 can include a resource coordination module 122for interference management and/or other suitable purposes. In oneexample, if base station 110 and terminal 120 are configured to utilizeoverlapping sets of control resources in time (e.g., subframes,interlaces, etc.), frequency (e.g., sub-bands, etc.), code, or the like,resource coordination modules 112 and/or 122 at base station 110 and/orterminal 120, respectively, can facilitate coordination between theoverlapping control resources such that transmissions conducted over theoverlapping resources from one entity in system 100 do not interferewith communication at another nearby entity. Specific techniques thatcan be utilized for resource coordination are provided in further detailinfra.

In accordance with one aspect, resource coordination modules 112 and/or122 can facilitate resource partitioning via, for example, splitting ofresources in time, frequency, etc., between entities in system 100. Inone example, resource coordination module 112 at base station 110 canact in cooperation with a reservation request module 114, which canrequest one or more interfering entities to be silent in particularfrequency sub-bands, subframes or interlaces in time, etc., on whichbase station 110 expects to receive information from terminals 120and/or other entities within system 100. Similarly, terminal 120 caninclude a reservation request module 124 that can act in cooperationwith resource coordination module 122 to request interfering entities insystem 100 to be silent on frequency sub-bands, subframes or interlacesin time, and/or other resources over which terminal 120 expects toreceive information. Accordingly, by way of specific, non-limitingexample, resource coordination module 122 and/or reservation requestmodule 124 at terminal 120 can be utilized to enable terminal 120 toestablish a connection with a serving base station in the presence ofother interfering base stations. In another example, resourcecoordination module 112 and base station 110 and/or resourcecoordination module 122 at terminal 120 can be utilized to coordinateusage of control resources and/or data resources between base station110 and terminal 120. Techniques that can be utilized by terminal 120for selecting a base station 110 with which to communicate, determiningresources to be cleared in connection with communicating with theselected base station 110, and the like are described in further detailinfra.

In one example, base station 110 and/or terminal 120 can coordinateresource usage between respective entities in system 100 bycommunicating Resource Utilization Messages (RUMs) to various entitiesin system 100. For example, base station 110 can submit a FL Special RUM(F-SRUM) to one or more terminals 120 to request reservation (e.g.,clearing or setting aside) of resources, and terminal 120 can requestresource reservation by submitting a RL Special RUM (R-SRUM) to one ormore base stations 110 in system 100. In one example, a RUM can specifyresources to be reserved by a receiving entity, and the receiving entitycan in turn reserve the specified resources in response to the message.Alternatively, a RUM can include a general request for resourcereservation, based on which a receiving entity can reserve apredetermined amount of resources.

In accordance with one aspect, base station 110 and terminal 120 canexchange RUMs in association with the establishment of communicationbetween base station 110 and terminal 120 in the following manner. Itshould be appreciated, however, that the following description isprovided by way of example and not limitation and that, unlessexplicitly stated otherwise, the claims are not intended to be limitedto such an example. In particular, to enable a connection with a desiredbase station 110, terminal 120 can transmit an Access Request command tothe base station 110 to schedule transmissions over a particular set ofresources. Additionally or alternatively, terminal 120 can convey anR-SRUM to other base stations (not shown) that are causing interferencein the requested resources to request that the other base stations clearthe desired resources. It can be appreciated that terminal 120 canutilize a R-SRUM in this manner due to the fact that the desired basestation 110 is to transmit messages to terminal 120 in the configuredresources and that, if other base stations transmit using the sameresources with higher power than the desired base station 110, terminal120 can be rendered unable to recover the transmissions from basestation 110. Accordingly, the use of R-SRUMs in this manner canestablish a clean downlink channel for transmission from a desired basestation 110 to terminal 120.

Additionally or alternatively, a base station 110 that receives anAccess Request command from a terminal 120 for a particular subbandand/or set of resources can subsequently transmit an F-SRUM requestingother terminals causing significant interference in the correspondingresources to clear those resources. Accordingly, it can be appreciatedthat the use of F-SRUMs by base station 110 can provide a clean uplinkchannel for terminal 120 to send messages to base station 110. Specifictechniques for transmitting Access Request, R-SRUM, F-SRUM messages areillustrated and described in the description and related drawings thatfollow.

In one example, terminal 120 can transmit respective Access Requestcommands and/or R-SRUMs to base station 110 over a Physical UplinkControl Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), aSounding Reference Signal (SRS), a Physical Random Access Channel(PRACH), a Low Reuse Access (LRA) channel, and/or any other suitablechannel. In another example, base station 110 can transmit one or moreF-SRUMs to terminal 120 using a Primary Broadcast Channel (PBCH), aPhysical Downlink Control Channel (PDCCH), a Physical Downlink SharedChannel (PDSCH), a Physical Hybrid ARQ (Automatic Repeat Request)Indicator Channel (PHICH), a System Information Block (SIB), a PrimarySynchronization Sequence (PSS), a Secondary Synchronization Sequence(SSS), a preamble channel such as a Low Reuse Preamble (LRP) channel orthe like, and/or any other suitable channel. In addition, it can beappreciated that any suitable signaling type, such as Layer 1 (L1)signaling, Layer 3 (L3) signaling, or the like, can be utilized by basestation 110 and/or terminal 120 in transmitting respective AccessRequest commands, R-SRUMs, and/or F-SRUMs as described herein.

In accordance with another specific example, terminal 120 can utilize apreamble message, such as a Low Reuse Preamble (LRP) message and/oranother suitable mechanism, to identify respective base stations 110within range of terminal 120. Based on this determination, terminal 120can identify a base station 110 to which to connect and/or other basestations 110 that are causing interference. Subsequently, terminal 120can submit an Access Request command to the desired base station 110 andR-SRUM messages to base stations 110 identified as causing interference.

In accordance with one aspect, base stations 110 in system 100communicate with their respectively served terminals and are notconfigured with resources to communicate with a given terminal 120 priorto submission of an Access Request. Similarly, terminals 120 in system100 are not configured with resources to be utilized for communicationwith respective non-serving base stations 110. Accordingly, in oneexample a clean channel can be established within system 100 that isutilized exclusively for access requests and/or resource reservationrequests. A clean channel can be established, for example, by dedicatingpart of the system bandwidth to an access channel such that thededicated portion is used exclusively for access requests and/orreservation requests. In one example, such resources can be cleared byall base stations 110 and/or terminals 120 that allow communication insuch dominant interference conditions. Accordingly, base stations 110and/or terminals 120 in system 100 can be configured to monitor thededicated resources for access requests, resource requests, or othermessages.

By way of specific example, information relating to resources on whichaccess request and/or resource reservation request signaling can betransmitted can be obtained by terminals 120 in system 100 over one ormore communication channels such as, for example, PDCCH, SIB(s), PBCH,LRP, and/or any other suitable channel(s). Further, it can beappreciated that one or more channels utilized by a terminal 120 inobtaining information relating to resources on which access requestand/or resource reservation request signaling can be transmitted can beconfigured as global channels such that the terminal 120 can obtain thenecessary information from any suitable base station 110 in system 100,including base stations other than a base station 110 with whichterminal 120 desires to connect. In another specific example, respectivebase stations 110 can reserve one or more PUCCH resource blocks (RBs)(e.g., at the edge of the system frequency band and/or at any otherappropriate resource location) for reception of R-SRUM and/or AccessRequest messages. Additionally or alternatively, clean resources forAccess Request and/or R-SRUM transmission can be obtained by reservingPUSCH resources. Further, on the downlink, it can be appreciated thatclean resources for resource utilization signaling can be obtained viascheduling of PDSCH resources by respective base stations 110 such thatno control and/or data transmissions are conducted to and/or fromrespective terminals 120 on the scheduled resources.

In accordance with another aspect, base stations 110 and/or terminals120 in system 100 can be configured to re-transmit information over adedicated clean channel in the event that multiple messages collide at agiven time, a message fails to be properly received by its intendedrecipient, and/or due to other suitable causes. Re-transmission can beperformed at intervals in time according to a time reuse pattern, whichcan be uniform and/or time-varying. In one example, time reuse can betriggered at a terminal 120 when a desired base station 110 fails toschedule terminal 120 due to lack of resources and/or other causes.Thus, for example, terminal 120 can be configured to re-transmit anaccess request upon expiration of a predetermined period of time ifscheduling of the terminal 120 has not occurred.

In accordance with another aspect, one or more base stations 110 and/orterminals 120 in system 100 can coordinate communication resources withthe aid of an external system controller (not shown), which can be, forexample, a management server or entity for system 100 and/or one or moreareas within system 100. In one example, such a system controller can bea Home Node B (HNB) Management Server (HMS) and/or another suitableentity, which can coordinate the use of one or more channels within agiven area (e.g., a neighborhood). In another example, a standalonesystem controller can communicate with base stations 110 and/orterminals 120 in system 100 via backhaul messaging and/or by any othersuitable means.

As further illustrated in system 100, base station 110 can include aprocessor 116 and/or a memory 118, which can be utilized to implementsome or all of the functionality of resource coordination module 112,reservation request module 114, and/or any other component(s) of basestation 110. Similarly, FIG. 1 illustrates that terminal 120 can includea processor 126 and/or memory 128 to implement some or all of thefunctionality of resource coordination module 122, reservation requestmodule 124, and/or any other component(s) of terminal 120.

Turning now to FIG. 5, a block diagram of an example system 500 forutilizing unicast messages for downlink resource coordination inaccordance with various aspects is illustrated. As shown in FIG. 5,system 500 can include a UE 510, which can be located in the presence ofa desired serving eNB 520 as well as one or more neighboring eNBs532-536 that are causing interference to UE 510. As further shown inFIG. 5, R-SRUM messages can be transmitted in a unicast fashion, suchthat an access request is provided to a desired serving eNB 520 andindividually tailored R-SRUMs are transmitted to respective interferingeNBs 532, 534, and 536. In one example, respective R-SRUMs provided tocorresponding eNBs 532-536 can include an identity of an intended eNB,particular resources to be vacated, and/or other suitable information.

In accordance with one aspect, unicast R-SRUMs as shown in system 500can be transmitted over a channel specifically reserved for R-SRUMsand/or a legacy channel (e.g., a Physical Random Access Channel(PRACH)). In one example, to transmit information to interfering eNBs532-536 on legacy channels, UE 510 can in some cases be required toobtain system parameters, such as bandwidth parameters or the like, bylistening to signals transmitted by respective eNBs 532-536. UE 510 may,in some cases, not be able to obtain parameters relating to allinterfering eNBs 532 simultaneously. Thus, in one example, a multi-stagetechnique can be employed for obtaining channel information andsubmitting respective R-SRUMs as illustrated by FIG. 6.

As FIG. 6 illustrates, a UE 610 in the presence of a serving eNB 620 andmultiple interfering eNBs 632-636 can obtain channel informationrelating to an eNB 632 to which UE 610 is able to connect as illustratedin diagram 602. An eNB 632 to which UE 610 initially extracts channelparameters can, but need not, be an eNB 632 that generates the strongestinterference observed at UE 610. Based on extracted channel information,UE 610 can submit an R-SRUM to eNB 632 to cause eNB 632 to set aside apredefined set of resources. Subsequent to eNB 632 reserving the definedresources, UE 610 can extract channel parameters from one or more othereNBs 634 and transmit corresponding R-SRUMs as illustrated by diagram604. In one example, a subsequent eNB 634 with which UE 610 communicatescan, but need not, be the eNB that produces the strongest interferenceas observed at UE 610 following reservation of resources by a previousstrongest interfering eNB 632. In one example, the process illustratedby diagrams 602-604 can subsequently continue for additional eNBs (e.g.,eNB 636 and/or other eNBs in system 600) in order to enable UE 610 torequest resource reservation at all eNBs 632-636 causing higher than athreshold amount of interference to UE 610.

Returning to FIG. 5, unicast R-SRUM messaging can additionally oralternatively be conducted by, for example, utilizing a clean channelthat can be utilized by any UE(s) 510 and/or other entities in system500 to transmit R-SRUM messaging. In one example, a clean channel usedfor R-SRUM messaging can be specifically allocated for R-SRUMs,configured to coincide with a channel reserved for Access Requestmessaging and/or other similar types of messaging, and/or allocated inany other suitable manner. For example, as illustrated by diagram 700 inFIG. 7, preamble messages, such as LRP messages 712-716, can betransmitted by respective eNBs on downlink bandwidth 702 associated witha Low Reuse Preamble (LRP) channel and/or any other suitable preamblechannel reserved for preamble messages such as LRP messages 712-716.Further, Access Request commands 722 to a desired eNB and/or R-SRUMs724-726 to one or more interfering eNBs can be transmitted by one ormore UEs on uplink bandwidth 704 such that the timing of messages722-726 are tied to the timing of LRPs 712-716 transmitted bycorresponding eNBs on downlink bandwidth 702 to increase efficiency andR-SRUM detection accuracy.

In one example, a unicast Access Request or R-SRUM message intended fora given eNB can be transmitted at a predetermined time period on uplinkbandwidth 704 following an LRP transmitted by the eNB on downlinkbandwidth 702. For example, diagram 700 illustrates that following a LRP712 communicated by eNB 0, an Access Request 722 intended for eNB 0 canbe transmitted on uplink bandwidth 704 at a predetermined period of timefollowing the LRP 712. Similarly, an R-SRUM 724 intended for interferingeNB 1 can be transmitted using uplink bandwidth 704 at a predeterminedamount of time following an LRP 714 provided by eNB 1. Accordingly, itcan be appreciated that respective base stations can be configured toscan for Access Request and/or R-SRUM messaging at limited segments intime following transmission of a LRP, thereby reducing the amount ofresources required for R-SRUM detection and reducing the probability ofdetecting an R-SRUM falsely. In one example, a predetermined amount oftime between transmission of an LRP and a corresponding R-SRUM can beuniform for all entities within an association system or can vary withtime and/or from entity to entity. In another example, Access Requestmessaging and R-SRUM messaging can be conducted on the same channel,such as the channel illustrated by diagram 700, or on differentchannels.

In a further example, Access Request messages and/or R-SRUMs can beconfigured for retransmission over uplink bandwidth 704 in the eventthat a collision occurs between such messages transmitted by multiplerespective UEs and/or any other failure event that prevents a responseto a transmitted message from being received by its intended recipient.

Turning now to FIG. 8, a block diagram of a system 800 for utilizingbroadcast messages for downlink resource coordination in accordance withvarious aspects is illustrated. As illustrated by system 800, a set ofbase stations 810 and/or 820 can provide coverage for a geographicalarea that includes a terminal 830. In accordance with one aspect, in theevent that one or more base stations 810 and/or 820 are causinginterference to terminal 830, terminal 830 can submit an R-SRUM to basestations 810 and 820 in a broadcast fashion. In accordance with oneaspect, the broadcast R-SRUM can be submitted as part of an AccessRequest message.

In contrast to the unicast R-SRUM messaging techniques illustrated byFIGS. 5-7, it can be appreciated that a broadcast R-SRUM as transmittedby terminal 830 can be generalized for multiple base stations 810 and820 within range of 830. Thus, for example, a broadcast R-SRUM caninclude information such as the identity of a desired serving basestation, a transmit power at which the R-SRUM is transmitted, subbandindexes and/or other information relating to desired resources, or thelike. Upon receipt of a broadcast R-SRUM at a base station 810 and/or820, the base station 810 and/or 820 can utilize an interferencecalculation module 812 and/or 822 to determine whether it is causing atleast a threshold level of interference to terminal 830. For example,interference calculation module 812 and/or 822 can measure a power levelat which the R-SRUM was received and compare the measured power level tothe transmit power level provided in the R-SRUM to calculate the pathloss from terminal 830 to the corresponding base station 810 and/or 820.Based on this information, interference calculation module 812 and/or822 can determine an extent to which its corresponding base station 810and/or 820 is interfering with terminal 830. If the determinedinterference is at least a threshold value, a corresponding resourcereservation module 814 and/or 824 can be utilized to set aside theresources specified in the R-SRUM.

Thus, in accordance with one aspect, it can be appreciated that theunicast R-SRUM mechanisms illustrated by FIGS. 5-7 and the broadcastR-SRUM mechanisms illustrated by FIG. 8 can differ in the entity thatcalculates interference caused to terminal 830. More particularly, asdescribed herein, interference calculation can be performedterminal-side in the case of unicast R-SRUM and network-side in the caseof broadcast R-SRUM.

Turning next to FIG. 9, a system 900 for conducting uplink resourcecoordination in accordance with various aspects is illustrated. Inaccordance with one aspect, system 900 can include respective UEs 910and/or 920 that can be located within the coverage area of an eNB 930.In one example, in the event that eNB 930 does not provide communicationservice to UEs 910 and/or 920, one or more UEs 910 and/or 920 can, insome cases, cause interference or jamming to eNB 930 on the uplink(e.g., as shown above with regard to FIG. 4). Thus, to manage the levelof interference observed at eNB 930, eNB can broadcast F-SRUM messagingto one or more UEs 910 and/or 920 in order to cause interfering UEs 910and/or 920 to set aside given resources in order to allow eNB 930 tocommunicate to its associated UEs.

In one example, F-SRUM communication can be conducted in a similarmanner to the broadcast R-SRUM communication illustrated by system 800.More particularly, eNB 930 can broadcast a F-SRUM to UEs 910 and/or 920that includes the transmit power used to transmit the F-SRUM, specificresources desired for use, and/or other information. Upon receiving aF-SRUM, respective interference calculation modules 912 and/or 922 candetermine an extent to which their respectively associated UEs 910and/or 920 are interfering with eNB 930 based on information in theF-SRUM. This can be done by, for example, comparing a transmit powerspecified in the F-SRUM to a power at which the F-SRUM is received. Upondetermining that the UE 910 and/or 920 is causing at least apredetermined amount of interference to eNB 930, a resource reservationmodule 914 and/or 924 can set aside some or all of the resources desiredby eNB 930.

In accordance with another aspect, F-SRUM messaging can be conducted byeNB 930 on a downlink channel allocated for preamble transmission. Byway of specific example as shown by diagram 1000 in FIG. 10, F-SRUMmessaging can be conducted over downlink resources allocated for apreamble channel, such as, for example, an LRP channel. In one example,a preamble channel can be configured as a common channel within acommunication system that is utilized by respective base stations inorder to aid UEs in identifying neighboring base stations. By way ofexample, respective base stations in an associated communication systemcan transmit corresponding LRP messages 1010 and/or 1030, which can bedetected by a UE in order to aid the UE in discovering the respectivebase stations. In one example, LRP messages 1010 and/or 1030 can betransmitted at random intervals on an associated LRP channel in order toreduce the likelihood of continued collisions between LRP messages 1010and 1030 from different base stations.

In one example, respective base stations in an associated communicationsystem can further be configured to transmit F-SRUM messages 1020 on theLRP channel with time reuse in addition to the LRP messages 1010 and/or1030. In an alternative example, base stations can integrate F-SRUMinformation into respective LRP messages 1010 and/or 1030 such thatrespective UEs are configured to obtain information corresponding to anF-SRUM within one or more corresponding LRP messages 1010 and/or 1030.

In an alternative example, F-SRUM messaging can be embedded in one ormore LRP messages 1010 and/or 1030 by, for example, including aparameter in the respective LRP messages 1010 and/or 1030 that indicateswhether the corresponding base station is loaded. By way of specificexample, a 1-bit loading indicator can be utilized within a LRP message1010 and/or 1030. In such an example, when an LRP message 1010 and/or1030 indicates loading, respective interfering UEs can be configured toclear respective resources that the base station that transmitted theLRP message 1010 and/or 1030 will need to establish a connection withone or more of its served UEs. Alternatively, if the LRP message 1010and/or 1030 does not indicate loading, the UEs can be configured tocontinue using the respective resources. In one example, respective UEscan determine if they are interfering with a base station correspondingto an LRP message 1010 and/or 1030 based on the power measured on theLRP message 1010 and/or 1030 or by any other suitable means.

Turning next to FIG. 11, a set of diagrams 1102-1104 are provided thatillustrate a technique for connecting to a network cell via anintervening cell in accordance with various aspects. In one example, asystem as illustrated by FIG. 11 can include a set of network cells 1112and 1114, each of which can be located within communication range of aUE 1120. In accordance with one aspect, UE 1120 may observe a powerlevel from a first cell 1112 that is lower than that from a second cell1114 due to, for example, relative distances from the cells 1112 and1114, differing cell types (e.g., macro, pico, or femto cell), or thelike. However, due to range extension, access restrictions, and/or otherreasons, UE 1120 can in some cases be configured to connect to a cell1112 with a relatively low observed power level. Such a connection canresult in interference, as generally described above. Further, in somecases, UE 1120 may lack the processing power or capability to coordinateresources between the respective cells 1112 and 1114 in order tomitigate such interference.

Accordingly, in one example UE 1120 can initially connect to anon-serving cell 1114 for the limited purpose of facilitating resourcecoordination, as shown in diagram 1102. Upon connection between cell1114 and UE 1120, cell 1114 can communicate with cell 1112 over thebackhaul and/or by other suitable means to coordinate resource usagebetween cells 1112 and 1114 to mitigate interference caused to UE 1120.Subsequent to resource coordination as illustrated by diagram 1102, thenon-serving cell 1114 for UE 1120 can facilitate a handoff to theserving cell 1112. By way of specific example, the procedure illustratedby FIG. 11 can be conducted in a scenario in which cell 1114 is arestricted femto cell, cell 1112 is a macro cell, and UE 1120 is barredfrom connecting to cell 1114. In such an example, the procedureillustrated by FIG. 11 can be utilized to enable UE 1120 to receiveaccess privileges from a femto cell 1114 to which UE 1120 has beenbarred for the limited purpose of negotiating a handoff to macro cell1112.

Referring now to FIGS. 12-18, methodologies that can be performed inaccordance with various aspects set forth herein are illustrated. While,for purposes of simplicity of explanation, the methodologies are shownand described as a series of acts, it is to be understood andappreciated that the methodologies are not limited by the order of acts,as some acts can, in accordance with one or more aspects, occur indifferent orders and/or concurrently with other acts from that shown anddescribed herein. For example, those skilled in the art will understandand appreciate that a methodology could alternatively be represented asa series of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with one or more aspects.

With reference to FIG. 12, illustrated is a methodology 1200 for unicastmessaging for downlink resource partitioning in a wireless communicationsystem (e.g., system 500). It is to be appreciated that methodology 1200can be performed by, for example, a terminal (e.g., UE 510) and/or anyother appropriate network device. Methodology 1200 begins at block 1202,wherein an access request is transmitted to a desired serving basestation (e.g., serving eNB 520) on a clean communication channel. Next,methodology 1200 can proceed to block 1204, wherein respective RUMs aretransmitted to one or more detected interfering base stations (e.g.,interfering eNBs 532-536). In one example, the access requesttransmitted at block 1202 and the RUMs transmitted at block 1204 canutilize time reuse such that, at block 1206, it is determined whetherresponses to the access request and the RUMs are received. If responsesto the access request and the RUMs have not been received, methodology1200 can proceed to block 1208, wherein the access request and the RUMsare re-transmitted based on a time reuse pattern, after which thedetermination at block 1206 can repeat. Otherwise, methodology 1200 canconclude.

FIG. 13 illustrates another methodology 1300 for utilizing unicastmessaging for downlink resource partitioning in a wireless communicationsystem. Methodology 1300 can be performed by, for example, a terminal(e.g., UE 610) and/or any other appropriate network device. Methodology1300 begins at block 1302, wherein a highest interfering eNB (e.g.,interfering eNB 632) is identified. Next, at block 1304, channelinformation relating to the eNB identified at block 1302 is observed. Atblock 1306, a message is transmitted to the identified eNB requestingreservation of specified resources (e.g., time intervals, subbands,etc.) based on the channel information observed at block 1304. A checkcan subsequently be performed at block 1308 to determine whether thespecified resources have been set aside by the identified eNB, and upona negative determination the transmission at block 1306 can be repeated.Otherwise, methodology 1300 can proceed to block 1310, wherein it isdetermined whether other interfering eNBs (e.g., eNBs 634-636) arepresent. If such eNBs are present, methodology 1300 can return to block1302 for processing of a next-highest interfering eNB (e.g., asillustrated in diagram 604).

FIG. 14 illustrates a further methodology 1400 for employing unicastmessaging in connection with downlink resource partitioning in awireless communication system. Methodology 1400 can be performed by, forexample, a UE and/or any other appropriate network device. Methodology1400 begins at block 1402, wherein a base station causing at least athreshold level of interference is identified. Next, at block 1404, amessage (e.g., LRP 712 or LRP 722) transmitted by the base stationidentified at block 1402 on a common channel (e.g., a LRP channel) isidentified. Methodology 1400 can then conclude at block 1406, wherein amessage (e.g., R-SRUM 714 or R-SRUM 724) requesting reservation ofresources by the base station identified at block 1402 is transmitted onthe common channel at a predetermined time following the messageidentified at block 1404.

FIG. 15 illustrates a methodology 1500 for transmitting broadcastresource coordination messaging on the uplink in a wirelesscommunication system. Methodology 1500 can be performed by, for example,a mobile terminal (e.g., terminal 830) and/or any other appropriatenetwork device. Methodology 1500 begins at block 1502, wherein a desiredserving Node B (e.g., base station 810 or 820) is selected. Next, atblock 1504, a set of resources designated for communication with theNode B selected at block 1502 is identified. Methodology 1500 can thenconclude at block 1506, wherein an access request is broadcasted thatincludes an identity of the selected Node B, a transmit power at whichthe access request is being communicated, and information relating tothe set of resources identified at block 1504.

Turning next to FIG. 16, a methodology 1600 for leveraging broadcastaccess request messaging provided by a mobile terminal (e.g., terminal830) in connection with downlink resource partitioning is illustrated.Methodology 1600 can be performed by, for example, a Node B (e.g., basestation 810 and/or 820) and/or any other appropriate network device.Methodology 1600 begins at block 1602, wherein a message that includesaccess request and R-SRUM information is received from a terminal. Next,at block 1604, it is determined whether the entity performingmethodology 1600 is designated in the message received at block 1602 asa desired Node B. If the entity performing methodology 1600 is sodesignated, methodology 1600 can conclude at block 1606, whereincommunication with the terminal is established.

If the entity performing methodology 1600 is not designated as thedesired Node B, methodology 1600 can instead proceed to block 1608,wherein a transmit power level provided in the message received at block1602 is compared to a power level at which the message was received. Atblock 1610, it is then determined from the comparison at block 1608whether the entity performing methodology 1600 is interfering with theterminal from which the access request/R-SRUM message was received. Ifless than a threshold amount of interference is identified at block1610, methodology 1600 can conclude. Otherwise, methodology 1600 canproceed to block 1612 prior to concluding, wherein resources specifiedin the message received at block 1602 are set aside by the entityperforming methodology 1600.

Referring to FIG. 17, a methodology 1700 for conducting uplink resourcepartitioning is illustrated. Methodology 1700 can be performed by, forexample, a base station (e.g., eNB 930) and/or any other appropriatenetwork device. Methodology 1700 begins at block 1702, wherein a LRPchannel utilized by an associated communication system is identified.Next, at block 1704, a transmit power level and resource indexinformation are selected. Methodology 1700 can then conclude at block1706, wherein a downlink RUM is transmitted (e.g., to UEs 910 and/or920) over the LRP channel (e.g., as illustrated by diagram 1000) thatidentifies the selected the transmit power level and resource indexinformation selected at block 1704.

FIG. 18 illustrates another methodology 1800 for uplink resourcepartitioning in a wireless communication system. Methodology 1800 can beperformed by, for example, a terminal (e.g., UE 910 and/or 920) and/orany other appropriate network device. Methodology 1800 begins at block1802, wherein F-SRUM messaging is received from a base station (e.g.,eNB 930). Next, at block 1804, a power level at which the F-SRUMmessaging was received at block 1802 is measured. At block 1806, atransmit power level specified in the F-SRUM messaging is then comparedto the power level measured at block 1804. At block 1808, it is thendetermined from the comparison at block 1806 whether an entityperforming methodology 1800 is interfering with the base station fromwhich the F-SRUM messaging was received at block 1802. If less than athreshold amount of interference is identified at block 1808,methodology 1800 can conclude. Otherwise, methodology 1800 can proceedto block 1810 prior to concluding, wherein resources specified in theF-SRUM messaging are set aside by the entity performing methodology1800.

Referring next to FIGS. 19-23, respective apparatus 1900-2300 thatfacilitate resource partitioning in a wireless communication system areillustrated. It is to be appreciated that apparatus 1900-2300 arerepresented as including functional blocks, which can be functionalblocks that represent functions implemented by a processor, software, orcombination thereof (e.g., firmware).

With reference first to FIG. 19, illustrated is an apparatus 1900 forconducting unicast downlink resource coordination signaling. Apparatus1900 can be implemented by a mobile terminal (e.g., UE 610) and/oranother suitable network device and can include a module 1902 foridentifying a desired serving Node B and one or more interfering NodeBs, a module 1904 for transmitting an access request to the desiredserving Node B, and a module 1906 for transmitting unicast resourcereservation requests to respective interfering Node Bs.

FIG. 20 illustrates an apparatus 2000 for conducting broadcast downlinkresource coordination signaling. Apparatus 2000 can be implemented by aUE (e.g., terminal 830) and/or another suitable network device and caninclude a module 2002 for identifying a base station with whichcommunication is to be established; a module 2004 for selecting a set ofresources and a transmit power level; and a module 2006 for broadcastingan access request that indicates the base station with whichcommunication is to be established, the selected set of resources, andthe selected transmit power level.

Turning to FIG. 21, an apparatus 2100 for processing uplink resourcepartitioning messages is illustrated. Apparatus 2100 can be implementedby a terminal (e.g., UE 910 and/or 920) and/or another suitable networkdevice and can include a module 2102 for receiving a downlink RUM from abase station, a module 2104 for comparing a transmit power levelspecified in the RUM to a power level at which the RUM was received, amodule 2106 for calculating an amount of interference caused to the basestation based on the comparison, and a module 2108 for reservingresources specified in the RUM if the calculated interference is greaterthan or equal to a threshold.

Referring next to FIG. 22, an apparatus 2200 for processing broadcastdownlink resource coordination messaging is illustrated. Apparatus 2200can be implemented by a Node B (e.g., base station 810 and/or 820)and/or another suitable network device and can include a module 2202 forreceiving an access request from a terminal, a module 2204 for comparinga transmit power level specified in the access request to a receivedpower level of the access request, a module 2206 for calculatinginterference caused to the terminal based on the comparison, and amodule 2208 for setting aside resources specified in the access requestif the calculated interference meets or exceeds a threshold.

FIG. 23 illustrates an apparatus 2300 for conducting uplink resourcecoordination signaling. Apparatus 2300 can be implemented by a basestation (e.g., eNB 930) and/or another suitable network device and caninclude a module 2302 for identifying resource index information and atransmit power and a module 2304 for transmitting a downlink RUM at theidentified transmit power that specifies the resource index informationand the transmit power.

With reference to FIG. 24, a timing diagram 2400 is provided thatillustrates an example access procedure that can be implemented inaccordance with various aspects herein. In one example, the procedureillustrated by timing diagram 2400 can be executed by a UE and eNB thatdesire to conduct an access procedure, one or more eNBs that causeinterference to the desired UE, and one or more UEs that causeinterference to the desired eNB. The procedure illustrated by diagram2400 can start at time 2402, wherein a UE preparing to conduct an accessprocedure detects respective eNBs in an associated communication system(e.g., through) and identifies desired and interfering eNBs.Subsequently, the desired UE can submit an Access Request to a desiredeNB at time 2404 and transmit respective R-SRUMs to interfering eNBs attime 2406 that indicate downlink resources on which the UE is to receivean indication of an access grant. Upon receiving respective R-SRUMs, oneor more interfering eNBs can clear DL resources indicated by the R-SRUMsat time 2408.

After an Access Request from the desired UE has been received by thedesired eNB, the desired eNB can respond by transmitting an Access Grantindication to the desired UE on the downlink resources cleared by R-SRUMat time 2410 and submitting respective F-SRUMs to interfering UEs attime 2412 that indicate a set of uplink resources on which the desiredUE will respond to the Access Grant indication. In one example, thedesired UE can repeat Access Request and R-SRUM transmission as shown attimes 2404-2406 until an Access Grant is received from the desired eNB.

In response to receiving respective F-SRUMs from the desired eNB at time2412, respective interfering UEs can clear the uplink resourcesspecified in the F-SRUMs at time 2414. Finally, at time 2416, thedesired UE can submit a response to the Access Grant indication back tothe desired eNB over the resources cleared at time 2414. In one example,the desired eNB can repeat Access Grant and F-SRUM transmission as shownat times 2410-2412 until a response to an Access Grant indication isreceived from the desired UE.

Turning to FIG. 25, an exemplary wireless communication system 2500 isillustrated. In one example, system 2500 can be configured to support anumber of users, in which various disclosed embodiments and aspects canbe implemented. As shown in FIG. 25, by way of example, system 2500 canprovide communication for multiple cells 2502, (e.g., macro cells 2502a-2502 g), with respective cells being serviced by corresponding accesspoints (AP) 2504 (e.g., APs 2504 a-2504 g). In one example, one or morecells can be further divided into respective sectors (not shown).

As FIG. 25 further illustrates, various access terminals (ATs) 2506,including ATs 2506 a-2506 k, can be dispersed throughout system 2500. Inone example, an AT 2506 can communicate with one or more APs 2504 on aforward link (FL) and/or a reverse link (RL) at a given moment,depending upon whether the AT is active and whether it is in softhandoff and/or another similar state. As used herein and generally inthe art, an AT 2506 can also be referred to as a user equipment (UE), amobile terminal, and/or any other suitable nomenclature. In accordancewith one aspect, system 2500 can provide service over a substantiallylarge geographic region. For example, macro cells 2502 a-2502 g canprovide coverage for a plurality of blocks in a neighborhood and/oranother similarly suitable coverage area.

Referring now to FIG. 26, a block diagram illustrating an examplewireless communication system 2600 in which various aspects describedherein can function is provided. In one example, system 2600 is amultiple-input multiple-output (MIMO) system that includes a transmittersystem 2610 and a receiver system 2650. It should be appreciated,however, that transmitter system 2610 and/or receiver system 2650 couldalso be applied to a multi-input single-output system wherein, forexample, multiple transmit antennas (e.g., on a base station), cantransmit one or more symbol streams to a single antenna device (e.g., amobile station). Additionally, it should be appreciated that aspects oftransmitter system 2610 and/or receiver system 2650 described hereincould be utilized in connection with a single output to single inputantenna system.

In accordance with one aspect, traffic data for a number of data streamsare provided at transmitter system 2610 from a data source 2612 to atransmit (TX) data processor 2614. In one example, each data stream canthen be transmitted via a respective transmit antenna 2624.Additionally, TX data processor 2614 can format, encode, and interleavetraffic data for each data stream based on a particular coding schemeselected for each respective data stream in order to provide coded data.In one example, the coded data for each data stream can then bemultiplexed with pilot data using OFDM techniques. The pilot data canbe, for example, a known data pattern that is processed in a knownmanner. Further, the pilot data can be used at receiver system 2650 toestimate channel response. Back at transmitter system 2610, themultiplexed pilot and coded data for each data stream can be modulated(i.e., symbol mapped) based on a particular modulation scheme (e.g.,BPSK, QSPK, M-PSK, or M-QAM) selected for each respective data stream inorder to provide modulation symbols. In one example, data rate, coding,and modulation for each data stream can be determined by instructionsperformed on and/or provided by processor 2630.

Next, modulation symbols for all data streams can be provided to a TXprocessor 2620, which can further process the modulation symbols (e.g.,for OFDM). TX MIMO processor 2620 can then provides N_(T) modulationsymbol streams to N_(T) transceivers 2622 a through 2622 t. In oneexample, each transceiver 2622 can receive and process a respectivesymbol stream to provide one or more analog signals. Each transceiver2622 can then further condition (e.g., amplify, filter, and upconvert)the analog signals to provide a modulated signal suitable fortransmission over a MIMO channel. Accordingly, N_(T) modulated signalsfrom transceivers 2622 a through 2622 t can then be transmitted fromN_(T) antennas 2624 a through 2624 t, respectively.

In accordance with another aspect, the transmitted modulated signals canbe received at receiver system 2650 by N_(R) antennas 2652 a through2652 r. The received signal from each antenna 2652 can then be providedto respective transceivers 2654. In one example, each transceiver 2654can condition (e.g., filter, amplify, and downconvert) a respectivereceived signal, digitize the conditioned signal to provide samples, andthen processes the samples to provide a corresponding “received” symbolstream. An RX MIMO/data processor 2660 can then receive and process theN_(R) received symbol streams from N_(R) transceivers 2654 based on aparticular receiver processing technique to provide N_(T) “detected”symbol streams. In one example, each detected symbol stream can includesymbols that are estimates of the modulation symbols transmitted for thecorresponding data stream. RX processor 2660 can then process eachsymbol stream at least in part by demodulating, deinterleaving, anddecoding each detected symbol stream to recover traffic data for acorresponding data stream. Thus, the processing by RX processor 2660 canbe complementary to that performed by TX MIMO processor 2620 and TX dataprocessor 2616 at transmitter system 2610. RX processor 2660 canadditionally provide processed symbol streams to a data sink 2664.

In accordance with one aspect, the channel response estimate generatedby RX processor 2660 can be used to perform space/time processing at thereceiver, adjust power levels, change modulation rates or schemes,and/or other appropriate actions. Additionally, RX processor 2660 canfurther estimate channel characteristics such as, for example,signal-to-noise-and-interference ratios (SNRs) of the detected symbolstreams. RX processor 2660 can then provide estimated channelcharacteristics to a processor 2670. In one example, RX processor 2660and/or processor 2670 can further derive an estimate of the “operating”SNR for the system. Processor 2670 can then provide channel stateinformation (CSI), which can comprise information regarding thecommunication link and/or the received data stream. This information caninclude, for example, the operating SNR. The CSI can then be processedby a TX data processor 2618, modulated by a modulator 2680, conditionedby transceivers 2654 a through 2654 r, and transmitted back totransmitter system 2610. In addition, a data source 2616 at receiversystem 2650 can provide additional data to be processed by TX dataprocessor 2618.

Back at transmitter system 2610, the modulated signals from receiversystem 2650 can then be received by antennas 2624, conditioned bytransceivers 2622, demodulated by a demodulator 2640, and processed by aRX data processor 2642 to recover the CSI reported by receiver system2650. In one example, the reported CSI can then be provided to processor2630 and used to determine data rates as well as coding and modulationschemes to be used for one or more data streams. The determined codingand modulation schemes can then be provided to transceivers 2622 forquantization and/or use in later transmissions to receiver system 2650.Additionally and/or alternatively, the reported CSI can be used byprocessor 2630 to generate various controls for TX data processor 2614and TX MIMO processor 2620. In another example, CSI and/or otherinformation processed by RX data processor 2642 can be provided to adata sink 2644.

In one example, processor 2630 at transmitter system 2610 and processor2670 at receiver system 2650 direct operation at their respectivesystems. Additionally, memory 2632 at transmitter system 2610 and memory2672 at receiver system 2650 can provide storage for program codes anddata used by processors 2630 and 2670, respectively. Further, atreceiver system 2650, various processing techniques can be used toprocess the N_(R) received signals to detect the N_(T) transmittedsymbol streams. These receiver processing techniques can include spatialand space-time receiver processing techniques, which can also bereferred to as equalization techniques, and/or “successivenulling/equalization and interference cancellation” receiver processingtechniques, which can also be referred to as “successive interferencecancellation” or “successive cancellation” receiver processingtechniques.

FIG. 27 illustrates an example communication system 2700 that enablesdeployment of access point base stations within a network environment.As shown in FIG. 27, system 2700 can include multiple access point basestations (e.g., femto cells or Home Node B units (HNBs)) such as, forexample, HNBs 2710. In one example, respective HNBs 2710 can beinstalled in a corresponding small scale network environment, such as,for example, one or more user residences 2730. Further, respective HNBs2710 can be configured to serve associated and/or alien UE(s) 2720. Inaccordance with one aspect, respective HNBs 2710 can be coupled to theInternet 2740 and a mobile operator core network 2750 via a DSL router,a cable modem, and/or another suitable device (not shown). In accordancewith one aspect, an owner of a femto cell or HNB 2710 can subscribe tomobile service, such as, for example, 3G/4G mobile service, offeredthrough mobile operator core network 2750. Accordingly, UE 2720 can beenabled to operate both in a macro cellular environment 2760 and in aresidential small scale network environment.

In one example, UE 2720 can be served by a set of Femto cells or HNBs2710 (e.g., HNBs 2710 that reside within a corresponding user residence2730) in addition to a macro cell mobile network 2760. As used hereinand generally in the art, a home femto cell is a base station on whichan AT or UE is authorized to operate on, a guest femto cell refers to abase station on which an AT or UE is temporarily authorized to operateon, and an alien femto cell is a base station on which the AT or UE isnot authorized to operate on. In accordance with one aspect, a femtocell or HNB 2710 can be deployed on a single frequency or on multiplefrequencies, which may overlap with respective macro cell frequencies.

It is to be understood that the aspects described herein can beimplemented by hardware, software, firmware, middleware, microcode, orany combination thereof. When the systems and/or methods are implementedin software, firmware, middleware or microcode, program code or codesegments, they can be stored in a machine-readable medium, such as astorage component. A code segment can represent a procedure, a function,a subprogram, a program, a routine, a subroutine, a module, a softwarepackage, a class, or any combination of instructions, data structures,or program statements. A code segment can be coupled to another codesegment or a hardware circuit by passing and/or receiving information,data, arguments, parameters, or memory contents. Information, arguments,parameters, data, etc. can be passed, forwarded, or transmitted usingany suitable means including memory sharing, message passing, tokenpassing, network transmission, etc.

For a software implementation, the techniques described herein can beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. The software codes can be storedin memory units and executed by processors. The memory unit can beimplemented within the processor or external to the processor, in whichcase it can be communicatively coupled to the processor via variousmeans as is known in the art.

What has been described above includes examples of one or more aspects.It is, of course, not possible to describe every conceivable combinationof components or methodologies for purposes of describing theaforementioned aspects, but one of ordinary skill in the art canrecognize that many further combinations and permutations of variousaspects are possible. Accordingly, the described aspects are intended toembrace all such alterations, modifications and variations that fallwithin the spirit and scope of the appended claims. Furthermore, to theextent that the term “includes” is used in either the detaileddescription or the claims, such term is intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim. Furthermore, the term“or” as used in either the detailed description or the claims is meantto be a “non-exclusive or.”

What is claimed is:
 1. A method for wireless communication by a userequipment (UE), comprising: transmitting an access request to a desiredserving base station; transmitting resource utilization messages (RUMs)to one or more interfering base stations; and retransmitting the accessrequest and the RUMs based on a time reuse pattern when the UE has notreceived a response to the access request and the RUMs.
 2. The method ofclaim of claim 1, wherein the access request is transmitted on a cleancommunication channel, utilized for interference management signaling.3. The method of claim 1, wherein the access request is transmitted on aLow Reuse Preamble (LRP) channel.
 4. A method for wireless communicationby a user equipment (UE), comprising: identifying a base station causinga highest amount of interference; observing channel information relatedto the identified base station; requesting reservation of resources bythe interfering base station based, at least on part, on the observedchannel information; and when one or more interfering base stationscausing at least a threshold amount of interference is identified,observing channel characteristics related to the one or more interferingbase stations, and requesting reservation of resources based, at leastin part, on the observed channel information for the respective basestations.
 5. The method of claim 4, wherein the resources are one oftime or frequency resources.
 6. The method of claim 4, furthercomprising: determining the resources have not been reserved by the basestation causing the highest amount of interference; and in response tothe determination, re-transmitting the request for reservation ofresources.
 7. An apparatus for wireless communication, comprising: meansfor transmitting an access request to a desired serving base station;means for transmitting resource utilization messages (RUMs) to one ormore interfering base stations; and means for retransmitting the accessrequest and the RUMs based on a time reuse pattern when a user equipment(UE) has not received a response to the access request and the RUMs. 8.The apparatus of claim of claim 7, wherein the access request istransmitted on a clean communication channel, utilized for interferencemanagement signaling.
 9. The apparatus of claim 7, wherein the accessrequest is transmitted on a Low Reuse Preamble (LRP) channel.
 10. Anapparatus for wireless communication, comprising: means for identifyinga base station causing a highest amount of interference; means forobserving channel information related to the identified base station;means for requesting reservation of resources by the interfering basestation based, at least on part, on the observed channel information;and when one or more interfering base stations causing at least athreshold amount of interference is identified, means for observingchannel characteristics related to the one or more interfering basestations, and means for requesting reservation of resources based, atleast in part, on the observed channel information for the respectivebase stations.
 11. The apparatus of claim 10, wherein the resources areone of time or frequency resources.
 12. The apparatus of claim 10,further comprising: means for determining the resources have not beenreserved by the base station causing the highest amount of interference;and in response to the determination, means for re-transmitting therequest for reservation of resources.
 13. An apparatus for wirelesscommunication comprising at least one processor configured to: transmitan access request to a desired serving base station; transmit resourceutilization messages (RUMs) to one or more interfering base stations;and retransmit the access request and the RUMs based on a time reusepattern when a user equipment (UE) has not received a response to theaccess request and the RUMs; and a memory coupled to the at least oneprocessor.
 14. The apparatus of claim of claim 13, wherein the accessrequest is transmitted on a clean communication channel, utilized forinterference management signaling.
 15. The apparatus of claim 13,wherein the access request is transmitted on a Low Reuse Preamble (LRP)channel.
 16. An apparatus for wireless communication comprising at leastone processor configured to: identify a base station causing a highestamount of interference; observe channel information related to theidentified base station; request reservation of resources by theinterfering base station based, at least on part, on the observedchannel information; and when one or more interfering base stationscausing at least a threshold amount of interference is identified,observe channel characteristics related to the one or more interferingbase stations, and request reservation of resources based, at least inpart, on the observed channel information for the respective basestations; and a memory coupled to the at least one processor.
 17. Theapparatus of claim 16, wherein the resources are one of time orfrequency resources.
 18. The apparatus of claim 16, wherein the at leastone processor is further configured to: determine the resources have notbeen reserved by the base station causing the highest amount ofinterference; and in response to the determination, re-transmit therequest for reservation of resources.
 19. A computer-program product forwireless communications, the computer-program product comprising anon-transitory computer-readable medium having code stored thereon, thecode executable by one or more processors for: transmitting an accessrequest to a desired serving base station; transmitting resourceutilization messages (RUMs) to one or more interfering base stations;and retransmitting the access request and the RUMs based on a time reusepattern when a user equipment (UE) has not received a response to theaccess request and the RUMs.
 20. The computer-program product of claimof claim 19, wherein the access request is transmitted on a cleancommunication channel, utilized for interference management signaling.21. The computer-program product of claim 19, wherein the access requestis transmitted on a Low Reuse Preamble (LRP) channel.
 22. Acomputer-program product for wireless communications, thecomputer-program product comprising a non-transitory computer-readablemedium having code stored thereon, the code executable by one or moreprocessors for: computer-program product for wireless communications,the computer-program product comprising a non-transitorycomputer-readable medium having code stored thereon, the code executableby one or more processors for: identifying a base station causing ahighest amount of interference; observing channel information related tothe identified base station; requesting reservation of resources by theinterfering base station based, at least on part, on the observedchannel information; and when one or more interfering base stationscausing at least a threshold amount of interference is identified,observing channel characteristics related to the one or more interferingbase stations, and requesting reservation of resources based, at leastin part, on the observed channel information for the respective basestations.
 23. The computer-program product of claim 22, wherein theresources are one of time or frequency resources.
 24. Thecomputer-program product of claim 22, wherein the one or more processorsare further configured to: determine the resources have not beenreserved by the base station causing the highest amount of interference;and in response to the determination, re-transmit the request forreservation of resources.